Storage system with multiple write journals supporting synchronous replication failure recovery

ABSTRACT

A storage system in one embodiment is configured to participate as a source storage system in a synchronous replication process with a target storage system. In conjunction with the synchronous replication process, the source storage system receives write requests from at least one host device. Responsive to a given write request being a multi-page write request, an entry is created in a first journal, where the first journal is utilized to ensure that the given write request is completed for all of the pages or for none of the pages. Responsive to the write request being a single-page write request, an entry is created in a second journal different than the first journal. An address-to-signature table is updated utilizing write data of the write request, and if the corresponding entry for the write request was created in the first journal, the entry is swapped from the first journal into the second journal, and the write data of the write request is sent to the target storage system.

FIELD

The field relates generally to information processing systems, and more particularly to storage in information processing systems.

BACKGROUND

Many information processing systems are configured to replicate data from a storage system at one site to a storage system at another site. In some cases, such arrangements are utilized to support disaster recovery functionality within the information processing system. For example, an enterprise may replicate data from a production data center to a disaster recovery data center. In the event of a disaster at the production site, applications can be started at the disaster recovery site using the data that has been replicated to that site so that the enterprise can continue its business.

Data replication in these and other contexts can be implemented using asynchronous replication at certain times and synchronous replication at other times. For example, asynchronous replication may be configured to periodically transfer data in multiple cycles from a source site to a target site, while synchronous replication may be configured to mirror host writes from the source site to the target site as the writes are made at the source site. Source and target storage systems can therefore each be configured to support both asynchronous and synchronous replication modes.

Conventional approaches to data replication can be problematic under certain conditions. For example, communication link failures or other types of failures occurring during synchronous replication can make it difficult to preserve target replica consistency without undermining system performance. In situations of this type, it may be necessary to perform a time-consuming full data re-synchronization of replicated storage objects between the source and target storage systems. Techniques are therefore needed that can provide significantly more efficient recovery from failures occurring during synchronous replication.

SUMMARY

Illustrative embodiments provide techniques for efficient recovery from a failure in a synchronous replication process carried out between source and target storage systems in an information processing system. A given such embodiment utilizes multiple distinct journals for journaling respective multi-page and single-page write requests in a manner that more accurately accounts for write requests that are already being processed or “in flight” when a failure occurs in the synchronous replication process. Such embodiments can advantageously provide more accurate and efficient recovery from synchronous replication failures than conventional approaches. The resilience and reliability of the synchronous replication process in the presence of failures is thereby enhanced.

These embodiments illustratively include a clustered implementation of a content addressable storage system having a distributed storage controller. Similar advantages can be provided in other types of storage systems.

In one embodiment, an apparatus comprises a storage system configured to participate as a source storage system in a synchronous replication process with a target storage system. In conjunction with the synchronous replication process, the source storage system is further configured to receive write requests from at least one host device, and to process each of the received write requests. Responsive to the write request being a multi-page write request, a corresponding entry is created in a first journal for the write request, where the first journal is utilized to ensure that the given write request is completed for all of the multiple pages or for none of the multiple pages. Responsive to the write request being a single-page write request, a corresponding entry is created in a second journal different than the first journal. An address-to-signature table is updated utilizing write data of the write request, and if the corresponding entry for the write request was created in the first journal, the entry is swapped from the first journal into the second journal, and the write data of the write request is sent to the target storage system. Responsive to a failure in the synchronous replication process, different sets of one or more recovery operations are performed based at least in part on whether or not there is at least one entry remaining in the first journal.

In some embodiments, the first journal comprises an atomic transaction write journal and the second journal comprises a synchronous replication write journal. Additional or alternative journals can be used in other embodiments. For example, at least one of the first and second journals may be implemented as a sub-type of an additional journal utilized in updating of the address-to-signature table.

The swapping of the entry from the first journal into the second journal is illustratively performed in an atomic manner that ensures that the entry is in only one of the journals at any given time.

Absent any failures, the first and second journals may be released responsive to successful completion of the synchronous replication process.

Different types of failures in the synchronous replication process can result in one or more entries remaining in the first journal, in which case both the first and second journals are utilized in the failure recovery process, or in the absence of any entries remaining in the first journal, in which case only the second journal is utilized in the failure recovery process.

For example, if the failure in the synchronous replication process occurs after creation of the corresponding entry in the first journal but prior to swapping of the entry from the first journal into the second journal, the set of one or more recovery operations performed responsive to the failure comprises a first recovery operation performed utilizing the first journal and a second recovery operation subsequently performed utilizing the second journal. This is an example of a failure that results in one or more entries remaining in the first journal.

As another example, if the failure in the synchronous replication process occurs after swapping of the entry from the first journal into the second journal, the set of one or more recovery operations performed responsive to the failure comprises a recovery operation performed utilizing the second journal but no recovery operation performed utilizing the first journal. This is an example of a failure that does not result in entries remaining in the first journal.

In some embodiments, the source storage system comprises a plurality of storage nodes each comprising one or more of the storage devices, with each of the storage nodes of the target storage system further comprising a set of processing modules configured to communicate over one or more networks with corresponding sets of processing modules on other ones of the storage nodes. The sets of processing modules of the storage nodes of the source storage system collectively comprise at least a portion of the storage controller of the source storage system. Each of the sets of processing modules illustratively comprises one or more control modules, one or more routing modules and one or more data modules, and at least one of the sets of processing modules comprises a management module. The address-to-signature table on a given one of the storage nodes is maintained by a corresponding one of the one or more control modules of that storage node.

In some embodiments, local copies of the first and second journals are stored on respective ones of the storage nodes. A given such local copy of the first or second journal for one of the storage nodes also represents a remote copy of that journal for one or more other ones of the storage nodes.

The address-to-signature table maintained by the source storage system in some embodiments more particularly comprises at least one address-to-hash table of the source storage system. The entries of the address-to-hash table comprise respective ones of a plurality of logical addresses in association with respective hash handles corresponding to respective content-based signatures of respective pages.

The source and target storage systems illustratively comprise respective content addressable storage systems having respective sets of non-volatile memory storage devices. For example, the storage devices of the source and target storage systems in such embodiments can be configured to collectively provide respective all-flash storage arrays. The source and target storage systems may be associated with respective source and target sites of the replication process. For example, the source site may comprise a production site data center and the target site may comprise a disaster recovery site data center. Numerous other storage system arrangements are possible in other embodiments.

These and other illustrative embodiments include, without limitation, apparatus, systems, methods and processor-readable storage media.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an information processing system comprising a content addressable storage system that utilizes multiple journals to support synchronous replication failure recovery in an illustrative embodiment.

FIG. 2 illustrates a portion of a distributed storage controller of a content addressable storage system showing one possible arrangement utilizing multiple journals to support synchronous replication failure recovery across multiple processing modules of the distributed storage controller.

FIGS. 3A and 3B are block diagrams showing different views of an information processing system comprising source and target storage systems configured to participate in a synchronous replication process in an illustrative embodiment. These two figures are collectively referred to herein as FIG. 3.

FIG. 4 is a flow diagram showing an example of utilization of multiple journals to support synchronous replication failure recovery in an illustrative embodiment.

FIGS. 5 and 6 show examples of processing platforms that may be utilized to implement at least a portion of an information processing system in illustrative embodiments.

DETAILED DESCRIPTION

Illustrative embodiments will be described herein with reference to exemplary information processing systems and associated computers, servers, storage devices and other processing devices. It is to be appreciated, however, that these and other embodiments are not restricted to the particular illustrative system and device configurations shown. Accordingly, the term “information processing system” as used herein is intended to be broadly construed, so as to encompass, for example, processing systems comprising cloud computing and storage systems, as well as other types of processing systems comprising various combinations of physical and virtual processing resources. An information processing system may therefore comprise, for example, at least one data center or other cloud-based system that includes one or more clouds hosting multiple tenants that share cloud resources. Numerous other types of enterprise computing and storage systems are also encompassed by the term “information processing system” as that term is broadly used herein.

FIG. 1 shows an information processing system 100 configured in accordance with an illustrative embodiment. The information processing system 100 comprises a computer system 101 that includes host devices 102-1, 102-2, . . . 102-N. The host devices 102 communicate over a network 104 with a content addressable storage system 105. The content addressable storage system 105 is an example of what is more generally referred to herein as a “storage system,” and it is to be appreciated that a wide variety of other types of storage systems can be used in other embodiments. The content addressable storage system 105 will be referred to in subsequent description herein as simply storage system 105.

The host devices 102 and storage system 105 illustratively comprise respective processing devices of one or more processing platforms. For example, the host devices 102 and the storage system 105 can each comprise one or more processing devices each having a processor and a memory, possibly implementing virtual machines and/or containers, although numerous other configurations are possible.

The host devices 102 and storage system 105 may be part of an enterprise computing and storage system, a cloud-based system or another type of system. For example, the host devices 102 and the storage system 105 can be part of cloud infrastructure such as an Amazon Web Services (AWS) system. Other examples of cloud-based systems that can be used to provide one or more of host devices 102 and storage system 105 include Google Cloud Platform (GCP) and Microsoft Azure.

The host devices 102 are configured to write data to and read data from the storage system 105. The host devices 102 and the storage system 105 may be implemented on a common processing platform, or on separate processing platforms. A wide variety of other types of host devices can be used in other embodiments.

The host devices 102 in some embodiments illustratively provide compute services such as execution of one or more applications on behalf of each of one or more users associated with respective ones of the host devices 102. In some embodiments, one or more of the host devices 102 illustratively comprise respective compute nodes of an enterprise computer system, cloud-based computer system or other arrangement of multiple compute nodes associated with respective users.

The term “user” herein is intended to be broadly construed so as to encompass numerous arrangements of human, hardware, software or firmware entities, as well as combinations of such entities. Compute and/or storage services may be provided for users under a platform-as-a-service (PaaS) model, although it is to be appreciated that numerous other cloud infrastructure arrangements could be used. Also, illustrative embodiments can be implemented outside of the cloud infrastructure context, as in the case of a stand-alone computing and storage system implemented within a given enterprise.

The network 104 is assumed to comprise a portion of a global computer network such as the Internet, although other types of networks can be part of the network 104, including a wide area network (WAN), a local area network (LAN), a satellite network, a telephone or cable network, a cellular network, a wireless network such as a WiFi or WiMAX network, or various portions or combinations of these and other types of networks. The network 104 in some embodiments therefore comprises combinations of multiple different types of networks each comprising processing devices configured to communicate using Internet Protocol (IP) or other communication protocols.

As a more particular example, some embodiments may utilize one or more high-speed local networks in which associated processing devices communicate with one another utilizing Peripheral Component Interconnect express (PCIe) cards of those devices, and networking protocols such as InfiniBand, Gigabit Ethernet or Fibre Channel. Numerous alternative networking arrangements are possible in a given embodiment, as will be appreciated by those skilled in the art.

The storage system 105 is accessible to the host devices 102 over the network 104. The storage system 105 comprises a plurality of storage devices 106 and an associated storage controller 108. The storage devices 106 illustratively store metadata pages 110 and user data pages 112. The user data pages 112 in some embodiments are organized into sets of logical units (LUNs) each accessible to one or more of the host devices 102. The LUNs may be viewed as examples of what are also referred to herein as logical storage volumes of the storage system 105.

The storage devices 106 illustratively comprise solid state drives (SSDs). Such SSDs are implemented using non-volatile memory (NVM) devices such as flash memory. Other types of NVM devices that can be used to implement at least a portion of the storage devices 106 include non-volatile random access memory (NVRAM), phase-change RAM (PC-RAM) and magnetic RAM (MRAM). These and various combinations of multiple different types of NVM devices may also be used.

However, it is to be appreciated that other types of storage devices can be used in other embodiments. For example, a given storage system as the term is broadly used herein can include a combination of different types of storage devices, as in the case of a multi-tier storage system comprising a flash-based fast tier and a disk-based capacity tier. In such an embodiment, each of the fast tier and the capacity tier of the multi-tier storage system comprises a plurality of storage devices with different types of storage devices being used in different ones of the storage tiers. For example, the fast tier may comprise flash drives while the capacity tier comprises hard disk drives. The particular storage devices used in a given storage tier may be varied in other embodiments, and multiple distinct storage device types may be used within a single storage tier. The term “storage device” as used herein is intended to be broadly construed, so as to encompass, for example, flash drives, solid state drives, hard disk drives, hybrid drives or other types of storage devices.

In some embodiments, the storage system 105 illustratively comprises a scale-out all-flash content addressable storage array such as an XtremIO™ storage array from Dell EMC of Hopkinton, Mass. For example, the storage system 105 can comprise an otherwise conventional XtremIO™ storage array or other type of content addressable storage system that is suitably modified to incorporate synchronous replication failure recovery functionality utilizing multiple write journals as disclosed herein. Other types of storage arrays, including by way of example VNX® and Symmetrix VMAX® storage arrays also from Dell EMC, can be used to implement storage system 105 in other embodiments.

The term “storage system” as used herein is therefore intended to be broadly construed, and should not be viewed as being limited to content addressable storage systems or flash-based storage systems. A given storage system as the term is broadly used herein can comprise, for example, network-attached storage (NAS), storage area networks (SANs), direct-attached storage (DAS) and distributed DAS, as well as combinations of these and other storage types, including software-defined storage.

Other particular types of storage products that can be used in implementing storage system 105 in illustrative embodiments include all-flash and hybrid flash storage arrays such as Unity™ software-defined storage products such as ScaleIO™ and ViPR®, cloud storage products such as Elastic Cloud Storage (ECS), object-based storage products such as Atmos®, and scale-out NAS clusters comprising Isilon® platform nodes and associated accelerators, all from Dell EMC. Combinations of multiple ones of these and other storage products can also be used in implementing a given storage system in an illustrative embodiment.

The storage system 105 in the FIG. 1 embodiment is implemented as at least a portion of a clustered storage system and includes a plurality of storage nodes 115 each comprising a corresponding subset of the storage devices 106. Other clustered storage system arrangements comprising multiple storage nodes can be used in other embodiments. A given clustered storage system may include not only storage nodes 115 but also additional storage nodes 120 coupled to network 104. Alternatively, such additional storage nodes 120 may be part of another clustered storage system of the system 100. Each of the storage nodes 115 of the storage system 105 is assumed to be implemented using at least one processing device comprising a processor coupled to a memory.

The storage controller 108 of the storage system 105 in the present embodiment is configured to control the implementation of functionality for synchronous replication failure recovery utilizing multiple write journals as disclosed herein. The storage controller 108 is assumed to comprise a type of “processing device” as that term is broadly used herein, and more particularly comprises at least one processor coupled to a memory. The storage system 105 under the control of the storage controller 108 is operative to participate as a source storage system in a replication process with a target storage system, as will be described in more detail below.

The storage controller 108 in this embodiment is implemented in a distributed manner so as to comprise a plurality of distributed storage controller components implemented on respective ones of the storage nodes 115. The storage controller 108 is therefore an example of what is more generally referred to herein as a “distributed storage controller.” Accordingly, in subsequent description herein, the storage controller 108 is more particularly referred to as a distributed storage controller. Other types of potentially non-distributed storage controllers can be used in other embodiments.

Each of the storage nodes 115 in this embodiment further comprises a set of processing modules configured to communicate over one or more networks with corresponding sets of processing modules on other ones of the storage nodes 115. The sets of processing modules of the storage nodes 115 collectively comprise at least a portion of the distributed storage controller 108 of the storage system 105.

The modules of the distributed storage controller 108 in the present embodiment more particularly comprise different sets of processing modules implemented on each of the storage nodes 115. The set of processing modules of each of the storage nodes 115 comprises at least a control module 108C, a data module 108D and a routing module 108R. The distributed storage controller 108 further comprises one or more management (“MGMT”) modules 108M. For example, only a single one of the storage nodes 115 may include a management module 108M. It is also possible that management modules 108M may be implemented on each of at least a subset of the storage nodes 115.

Each of the storage nodes 115 of the storage system 105 therefore comprises a set of processing modules configured to communicate over one or more networks with corresponding sets of processing modules on other ones of the storage nodes. A given such set of processing modules implemented on a particular storage node illustratively includes at least one control module 108C, at least one data module 108D and at least one routing module 108R, and possibly a management module 108M. These sets of processing modules of the storage nodes collectively comprise at least a portion of the distributed storage controller 108.

Communication links may be established between the various processing modules of the distributed storage controller 108 using well-known communication protocols such as IP and Transmission Control Protocol (TCP). For example, respective sets of IP links used in data transfer and corresponding messaging could be associated with respective different ones of the routing modules 108R.

The storage devices 106 are configured to store metadata pages 110 and user data pages 112, and may also store additional information not explicitly shown such as checkpoints and write journals. The metadata pages 110 and the user data pages 112 are illustratively stored in respective designated metadata and user data areas of the storage devices 106. Accordingly, metadata pages 110 and user data pages 112 may be viewed as corresponding to respective designated metadata and user data areas of the storage devices 106.

The term “page” as used herein is intended to be broadly construed so as to encompass any of a wide variety of different types of blocks that may be utilized in a block storage device of a storage system. Such storage systems are not limited to content addressable storage systems of the type disclosed in some embodiments herein, but are more generally applicable to any storage system that includes one or more block storage devices. Different native page sizes are generally utilized in different storage systems of different types. For example, XtremIO™ X1 storage arrays utilize a native page size of 8 KB, while XtremIO™ X2 storage arrays utilize a native page size of 16 KB. Larger native page sizes of 64 KB and 128 KB are utilized in VMAX® V2 and VMAX® V3 storage arrays, respectively. The native page size generally refers to a typical page size at which the storage system ordinarily operates, although it is possible that some storage systems may support multiple distinct page sizes as a configurable parameter of the system. Each such page size of a given storage system may be considered a “native page size” of the storage system as that term is broadly used herein.

A given “page” as the term is broadly used herein should therefore not be viewed as being limited to any particular range of fixed sizes. In some embodiments, a page size of 8 KB is used, but this is by way of example only and can be varied in other embodiments. For example, page sizes of 4 KB, 16 KB or other values can be used. Accordingly, illustrative embodiments can utilize any of a wide variety of alternative paging arrangements for organizing the metadata pages 110 and the user data pages 112.

The user data pages 112 are part of a plurality of LUNs configured to store files, blocks, objects or other arrangements of data, each also generally referred to herein as a “data item,” on behalf of users associated with host devices 102. Each such LUN may comprise particular ones of the above-noted pages of the user data area. The user data stored in the user data pages 112 can include any type of user data that may be utilized in the system 100. The term “user data” herein is therefore also intended to be broadly construed.

The storage system 105 is configured to generate hash metadata providing a mapping between content-based digests of respective ones of the user data pages 112 and corresponding physical locations of those pages in the user data area. Content-based digests generated using hash functions are also referred to herein as “hash digests.” Such hash digests or other types of content-based digests are examples of what are more generally referred to herein as “content-based signatures” of the respective user data pages 112. The hash metadata generated by the storage system 105 is illustratively stored as metadata pages 110 in the metadata area. The generation and storage of the hash metadata is assumed to be performed under the control of the distributed storage controller 108.

Each of the metadata pages 110 characterizes a plurality of the user data pages 112. For example, a given set of user data pages representing a portion of the user data pages 112 illustratively comprises a plurality of user data pages denoted User Data Page 1, User Data Page 2, . . . User Data Page n.

Each of the user data pages 112 in this example is characterized by a LUN identifier, an offset and a content-based signature. The content-based signature is generated as a hash function of content of the corresponding user data page. Illustrative hash functions that may be used to generate the content-based signature include the above-noted SHA1 hash function, or other secure hashing algorithms known to those skilled in the art. The content-based signature is utilized to determine the location of the corresponding user data page within the user data area of the storage devices 106.

Each of the metadata pages 110 in the present embodiment is assumed to have a signature that is not content-based. For example, the metadata page signatures may be generated using hash functions or other signature generation algorithms that do not utilize content of the metadata pages as input to the signature generation algorithm. Also, each of the metadata pages is assumed to characterize a different set of the user data pages.

A given set of metadata pages representing a portion of the metadata pages 110 in an illustrative embodiment comprises metadata pages denoted Metadata Page 1, Metadata Page 2, . . . Metadata Page m, having respective signatures denoted Signature 1, Signature 2, . . . Signature m. Each such metadata page characterizes a different set of n user data pages. For example, the characterizing information in each metadata page can include the LUN identifiers, offsets and content-based signatures for each of the n user data pages that are characterized by that metadata page. It is to be appreciated, however, that the user data and metadata page configurations described above are examples only, and numerous alternative user data and metadata page configurations can be used in other embodiments.

Ownership of a user data logical address space within the storage system 105 is illustratively distributed among the control modules 108C.

The synchronous replication failure recovery functionality utilizing multiple journals in this embodiment is assumed to be distributed across multiple distributed processing modules, including at least a subset of the processing modules 108C, 108D, 108R and 108M of the distributed storage controller 108.

For example, the management module 108M of the distributed storage controller 108 may include replication control logic that engages or otherwise interacts with corresponding control logic instances in all of the control modules 108C and routing modules 108R in order to implement a synchronous replication process.

In some embodiments, the storage system 105 comprises an XtremIO™ storage array suitably modified to incorporate techniques for synchronous replication failure recovery utilizing multiple write journals as disclosed herein.

In arrangements of this type, the control modules 108C, data modules 108D and routing modules 108R of the distributed storage controller 108 illustratively comprise respective C-modules, D-modules and R-modules of the XtremIO™ storage array. The one or more management modules 108M of the distributed storage controller 108 in such arrangements illustratively comprise a system-wide management module (“SYM module”) of the XtremIO™ storage array, although other types and arrangements of system-wide management modules can be used in other embodiments. Accordingly, synchronous replication failure recovery functionality utilizing multiple journals in some embodiments is implemented under the control of at least one system-wide management module of the distributed storage controller 108, utilizing the C-modules, D-modules and R-modules of the XtremIO™ storage array.

In the above-described XtremIO™ storage array example, each user data page has a fixed size such as 8 KB and its content-based signature is a 20-byte signature generated using an SHA1 hash function. Also, each page has a LUN identifier and an offset, and so is characterized by <lun_id, offset, signature>.

The content-based signature in the present example comprises a content-based digest of the corresponding data page. Such a content-based digest is more particularly referred to as a “hash digest” of the corresponding data page, as the content-based signature is illustratively generated by applying a hash function such as SHA1 to the content of that data page. The full hash digest of a given data page is given by the above-noted 20-byte signature. The hash digest may be represented by a corresponding “hash handle,” which in some cases may comprise a particular portion of the hash digest. The hash handle illustratively maps on a one-to-one basis to the corresponding full hash digest within a designated cluster boundary or other specified storage resource boundary of a given storage system. In arrangements of this type, the hash handle provides a lightweight mechanism for uniquely identifying the corresponding full hash digest and its associated data page within the specified storage resource boundary. The hash digest and hash handle are both considered examples of “content-based signatures” as that term is broadly used herein.

Examples of techniques for generating and processing hash handles for respective hash digests of respective data pages are disclosed in U.S. Pat. No. 9,208,162, entitled “Generating a Short Hash Handle,” and U.S. Pat. No. 9,286,003, entitled “Method and Apparatus for Creating a Short Hash Handle Highly Correlated with a Globally-Unique Hash Signature,” both of which are incorporated by reference herein.

As mentioned previously, storage controller components in an XtremIO™ storage array illustratively include C-module, D-module and R-module components. For example, separate instances of such components can be associated with each of a plurality of storage nodes in a clustered storage system implementation.

The distributed storage controller 108 in this example is configured to group consecutive pages into page groups, to arrange the page groups into slices, and to assign the slices to different ones of the C-modules. For example, if there are 1024 slices distributed evenly across the C-modules, and there are a total of 16 C-modules in a given implementation, each of the C-modules “owns” 1024/16=64 slices. In such arrangements, different ones of the slices are assigned to different ones of the control modules 108C such that control of the slices within the distributed storage controller 108 is substantially evenly distributed over the control modules 108C of the distributed storage controller 108.

The D-module allows a user to locate a given user data page based on its signature. Each metadata page also has a size of 8 KB and includes multiple instances of the <lun_id, offset, signature> for respective ones of a plurality of the user data pages. Such metadata pages are illustratively generated by the C-module but are accessed using the D-module based on a metadata page signature.

The metadata page signature in this embodiment is a 20-byte signature but is not based on the content of the metadata page. Instead, the metadata page signature is generated based on an 8-byte metadata page identifier that is a function of the LUN identifier and offset information of that metadata page.

If a user wants to read a user data page having a particular LUN identifier and offset, the corresponding metadata page identifier is first determined, then the metadata page signature is computed for the identified metadata page, and then the metadata page is read using the computed signature. In this embodiment, the metadata page signature is more particularly computed using a signature generation algorithm that generates the signature to include a hash of the 8-byte metadata page identifier, one or more ASCII codes for particular predetermined characters, as well as possible additional fields. The last bit of the metadata page signature may always be set to a particular logic value so as to distinguish it from the user data page signature in which the last bit may always be set to the opposite logic value.

The metadata page signature is used to retrieve the metadata page via the D-module. This metadata page will include the <lun_id, offset, signature> for the user data page if the user page exists. The signature of the user data page is then used to retrieve that user data page, also via the D-module.

Write requests processed in the storage system 105 each illustratively comprise one or more IO operations directing that at least one data item of the storage system 105 be written to in a particular manner. A given write request is illustratively received in the storage system 105 from a host device, illustratively one of the host devices 102. In some embodiments, a write request is received in the distributed storage controller 108 of the storage system 105, and directed from one processing module to another processing module of the distributed storage controller 108. For example, a received write request may be directed from a routing module 108R of the distributed storage controller 108 to a particular control module 108C of the distributed storage controller 108. Other arrangements for receiving and processing write requests from one or more host devices can be used.

The term “write request” as used herein is intended to be broadly construed, so as to encompass one or more IO operations directing that at least one data item of a storage system be written to in a particular manner. A given write request is illustratively received in a storage system from a host device.

In the XtremIO™ context, the C-modules, D-modules and R-modules of the storage nodes 115 communicate with one another over a high-speed internal network such as an InfiniBand network. The C-modules, D-modules and R-modules coordinate with one another to accomplish various IO processing tasks.

The write requests from the host devices identify particular data pages to be written in the storage system 105 by their corresponding logical addresses each comprising a LUN ID and an offset.

As noted above, a given one of the content-based signatures illustratively comprises a hash digest of the corresponding data page, with the hash digest being generated by applying a hash function to the content of that data page. The hash digest may be uniquely represented within a given storage resource boundary by a corresponding hash handle.

The storage system 105 utilizes a two-level mapping process to map logical block addresses to physical block addresses. The first level of mapping uses an address-to-hash (“A2H”) table and the second level of mapping uses a hash metadata (“HMD”) table, with the A2H and HMD tables corresponding to respective logical and physical layers of the content-based signature mapping within the storage system 105.

The first level of mapping using the A2H table associates logical addresses of respective data pages with respective content-based signatures of those data pages. This is also referred to logical layer mapping.

The second level of mapping using the HMD table associates respective ones of the content-based signatures with respective physical storage locations in one or more of the storage devices 106. This is also referred to as physical layer mapping.

For a given write request, both of the corresponding HMD and A2H tables are updated in conjunction with the processing of that write request.

The A2H and HMD tables described above are examples of what are more generally referred to herein as “mapping tables” of respective first and second distinct types. Other types and arrangements of mapping tables or other content-based signature mapping information may be used in other embodiments.

The logical block addresses or LBAs of a logical layer of the storage system 105 correspond to respective physical blocks of a physical layer of the storage system 105. The user data pages of the logical layer are organized by LBA and have reference via respective content-based signatures to particular physical blocks of the physical layer.

Each of the physical blocks has an associated reference count that is maintained within the storage system 105. The reference count for a given physical block indicates the number of logical blocks that point to that same physical block.

In releasing logical address space in the storage system, a dereferencing operation is generally executed for each of the LBAs being released. More particularly, the reference count of the corresponding physical block is decremented. A reference count of zero indicates that there are no longer any logical blocks that reference the corresponding physical block, and so that physical block can be released.

It should also be understood that the particular arrangement of storage controller processing modules 108C, 108D, 108R and 108M as shown in the FIG. 1 embodiment is presented by way of example only. Numerous alternative arrangements of processing modules of a distributed storage controller may be used to implement synchronous replication failure recovery functionality utilizing multiple write journals in a clustered storage system in other embodiments.

Additional examples of content addressable storage functionality implemented in some embodiments by control modules 108C, data modules 108D, routing modules 108R and management module(s) 108M of distributed storage controller 108 can be found in U.S. Pat. No. 9,104,326, entitled “Scalable Block Data Storage Using Content Addressing,” which is incorporated by reference herein. Alternative arrangements of these and other storage node processing modules of a distributed storage controller in a content addressable storage system can be used in other embodiments.

The storage controller 108 of storage system 105 in the FIG. 1 embodiment includes replication control logic that is illustratively implemented in a distributed manner utilizing at least a subset of the control modules 108C, data modules 108D, routing modules 108R and management module(s) 108M. Other types of replication control logic can be implemented in the storage controller 108 in other embodiments. For example, the replication control logic in some embodiments comprises a replication engine that in some implementations is in the form of a separate module.

The storage controller 108 and storage system 105 should also be understood to include additional modules and other components typically found in conventional implementations of storage controllers and storage systems, although such additional modules and other components are omitted from the figure for clarity and simplicity of illustration.

The storage controller 108 via its replication control logic is configured to operate as a source storage system in a replication process carried out with a target storage system that is not explicitly shown in the figure but may be coupled to network 104 and may comprise at least a subset of the additional storage nodes 120. The replication process illustratively comprises a synchronous replication process that is initiated in the source storage system to replicate one or more logical storage volumes from the source storage system to the target storage system. The synchronous replication process initiated in the storage system 105 is illustratively configured to replicate one or more production storage volumes to corresponding recovery storage volumes of the target storage system. The target storage system in some embodiments is assumed to comprise a clustered storage system having a plurality of storage nodes implementing a distributed storage controller substantially the same as distributed storage controller 108 of storage system 105.

The synchronous replication in some embodiments is configured such that host write operations directed to the production storage volumes of the source storage system by one or more of the host devices 102 are mirrored to the corresponding recovery storage volumes of the target storage system.

More particularly, in this embodiment, the storage controller 108 of the source storage system comprises replication control logic configured to cooperatively interact with corresponding replication control logic in a storage controller of the target storage system in order to execute at least a synchronous replication process carried out between the source and target storage systems. The target storage system can be implemented on the same processing platform as the source storage system or on a different processing platform. The replication control logic of a given one of the source and target storage systems may comprise software, hardware or firmware, or combinations thereof, implemented in one or more storage node processing modules, such as control modules, data modules, routing modules and management modules of a distributed storage controller of the corresponding storage system.

The synchronous replication process can more particularly comprise a synchronous replication mode of a multiple-mode replication process that includes both asynchronous and synchronous replication modes. For example, a given such multiple-mode replication process can comprise a cycle-based asynchronous replication mode in which differential data derived from snapshots of the production storage volumes of the source storage system is utilized to update the corresponding recovery storage volumes of the target storage system in each of a plurality of replication cycles.

A given “replication process” as that term is broadly used herein may therefore include both asynchronous and synchronous replication modes of a multiple-mode replication process as well as support for concurrent operation of such modes and separate operation of the individual modes. The term “mode” as used herein in conjunction with asynchronous or synchronous replication may therefore itself comprise a corresponding asynchronous or synchronous replication process.

The replication process is illustratively configured to replicate particular designated production storage volumes or other logical storage volumes of the storage system 105 to the target storage system. A given such production storage volume designated for replication by the storage system 105 illustratively comprises a set of one or more LUNs or other logical storage volumes of the storage system 105. Each such logical storage volume comprises at least a portion of a physical storage space of one or more of the storage devices 106. Other arrangements of one or more storage volumes may be designated for replication as part of a given replication process in other embodiments.

In conjunction with the replication process, the storage system 105 operating as a source storage system is configured to receive write requests from at least one of the host devices 102, and for each of the received write requests, to journal the write request in one of first and second distinct journals, depending upon whether the write request is a multi-page write request or a single-page write request. The first and second journals may be distinct journals maintained in a common journaling system of the storage system 105. For example, at least one of the first and second journals may be implemented as a sub-type of one or more other journals maintained by the journaling system.

A new sub-type of an existing journal can be deployed in a simple and inexpensive manner utilizing additional bit values in a portion of memory already allocated for the existing journal. Moreover, the use of a sub-type of an existing journal preserves backwards compatibility with prior storage system software versions.

The page or pages identified by a given write request for which an entry is created in either the first or second journal illustratively comprise at least a portion of at least one LUN comprising multiple ones of the user data pages 112.

Responsive to the write request being a multi-page write request, the storage system 105 creates a corresponding entry in the first journal for the write request, where the first journal is utilized to ensure that the given write request is completed for all of the multiple pages or for none of the multiple pages. The first journal in some embodiments more particularly comprises an atomic transaction write journal.

Responsive to the write request being a single-page write request, the storage system 105 creates a corresponding entry in the second journal, which as noted above is a different journal than the first journal. The second journal in some embodiments more particularly comprises a synchronous replication write journal.

The storage system 105 updates an A2H table or other type of address-to-signature table utilizing write data of the write request, and if the corresponding entry for the write request was created in the first journal, the storage system 105 swaps the entry from the first journal into the second journal. The storage system 105 sends the write data of the write request to the target storage system.

The swapping of the entry from the first journal into the second journal is illustratively performed in an atomic manner that ensures that the entry is in only one of the journals at any given time.

The first and second journals are illustratively released responsive to successful completion of the synchronous replication process. Such release may more particularly involve “cleaning up” the journals.

Responsive to a failure in the synchronous replication process, different sets of one or more recovery operations are performed based at least in part on whether or not there is at least one entry remaining in the first journal.

For example, if the failure in the synchronous replication process occurs after creation of the corresponding entry in the first journal but prior to swapping of the entry from the first journal into the second journal, the set of one or more recovery operations performed responsive to the failure comprises a first recovery operation performed utilizing the first journal and a second recovery operation subsequently performed utilizing the second journal.

As another example, if the failure in the synchronous replication process occurs after swapping of the entry from the first journal into the second journal, the set of one or more recovery operations performed responsive to the failure comprises a recovery operation performed utilizing the second journal but no recovery operation performed utilizing the first journal.

Local copies of the first and second journals are illustratively stored on respective ones of the storage nodes 115 of the storage system 105. A given such local copy of the first or second journal for one of the storage nodes 115 also represents a remote copy of that journal for one or more other ones of the storage nodes 115. Local and remote copies are therefore typically on different ones of the storage nodes 115.

Instances of the journals associated with respective ones of the storage nodes 115 therefore include multiple copies, one local and one remote. For example, different ones of the control modules 108C illustratively maintain local copies of respective ones of the first and second journals. Corresponding remote copies are located in a manner selected to preserve accessibility to the journals in the event of a failure in one or more of the storage nodes maintaining respective local copies. If a given local copy is not available due to a node failure or other similar issue, the corresponding remote copy is used. Different remote location algorithms may be utilized to determine appropriate remote locations for different journal types. Data transfer between local and remote copies is implemented via remote direct memory access (RDMA) or other rapid data transfer mechanisms.

As noted above, at least one of the first and second journals is implemented as a sub-type of an additional journal of the storage system 105. This additional journal illustratively comprises a journal utilized in updating of the A2H table or other type of address-to-signature table of the storage system 105.

The address-to-signature table maintained by the source storage system therefore in some embodiments comprises at least one A2H table of the source storage system. A given such A2H table as described elsewhere herein has entries comprising respective ones of a plurality of logical addresses in association with respective hash handles corresponding to respective content-based signatures.

As indicated previously, the host devices 102 and storage system 105 in the FIG. 1 embodiment are assumed to be implemented using at least one processing platform each comprising one or more processing devices each having a processor coupled to a memory. Such processing devices can illustratively include particular arrangements of compute, storage and network resources.

The host devices 102 and the storage system 105 may be implemented on respective distinct processing platforms, although numerous other arrangements are possible. For example, in some embodiments at least portions of the host devices 102 and the storage system 105 are implemented on the same processing platform. The storage system 105 can therefore be implemented at least in part within at least one processing platform that implements at least a one of the host devices 102.

The term “processing platform” as used herein is intended to be broadly construed so as to encompass, by way of illustration and without limitation, multiple sets of processing devices and associated storage systems that are configured to communicate over one or more networks. For example, distributed implementations of the system 100 are possible, in which certain components of the system reside in one data center in a first geographic location while other components of the system reside in one or more other data centers in one or more other geographic locations that are potentially remote from the first geographic location. Thus, it is possible in some implementations of the system 100 for the host devices 102 and the storage system 105 to reside in different data centers. Numerous other distributed implementations of the host devices 102 and/or the storage system 105 are possible. Accordingly, the storage system 105 can also be implemented in a distributed manner across multiple data centers.

Additional examples of processing platforms utilized to implement host devices and/or storage systems in illustrative embodiments will be described in more detail below in conjunction with FIGS. 5 and 6.

It is to be appreciated that these and other features of illustrative embodiments are presented by way of example only, and should not be construed as limiting in any way.

Accordingly, different numbers, types and arrangements of system components such as host devices 102, network 104, storage system 105, storage devices 106, storage controllers 108 and storage nodes 115 can be used in other embodiments.

It should be understood that the particular sets of modules and other components implemented in the system 100 as illustrated in FIG. 1 are presented by way of example only. In other embodiments, only subsets of these components, or additional or alternative sets of components, may be used, and such components may exhibit alternative functionality and configurations.

For example, in some embodiments, at least portions of the functionality for synchronous replication failure recovery utilizing multiple journals as disclosed herein can be implemented in a host device, in a storage system, or partially in a host device and partially in a storage system.

Accordingly, illustrative embodiments are not limited to arrangements in which all such functionality is implemented in a host device or a storage system, and therefore encompass various hybrid arrangements in which the functionality is distributed over one or more host devices and one or more storage systems, each comprising one or more processing devices.

Referring now to FIG. 2, a more detailed view of a portion of the distributed storage controller 108 in an illustrative embodiment is shown. This embodiment illustrates an example arrangement of control modules 108C and data modules 108D of the distributed storage controller 108.

The management module 108M of the distributed storage controller 108 in this embodiment more particularly comprises a system-wide management module or SYM module of the type mentioned previously. Although only a single SYM module is shown in this embodiment, other embodiments can include multiple instances of the SYM module possibly implemented on different ones of the storage nodes. It is therefore assumed that the distributed storage controller 108 comprises one or more management modules 108M.

A given instance of management module 108M comprises replication control logic 200 and associated management program code 202. The management module 108M communicates with control modules 108C-1 through 108C-x, also denoted as C-module 1 through C-module x. The control modules 108C communicate with data modules 108D-1 through 108D-y, also denoted as D-module 1 through D-module y. The variables x and y are arbitrary integers greater than one, and may but need not be equal. In some embodiments, each of the storage nodes 115 of the storage system 105 comprises one of the control modules 108C and one of the data modules 108D, as well as one or more additional modules including one of the routing modules 108R.

The control modules 108C-1 through 108C-x in the FIG. 2 embodiment comprise respective write journals 204C-1 through 204C-x. These write journals 204C are utilized by corresponding instances of replication control logic 206C-1 through 206C-x to support failure recovery in conjunction with a synchronous replication process. For example, the write journals 204C illustratively comprise separate journals referred to herein as an atomic transaction write journal and a synchronous replication write journal.

The control modules 108C may further comprise additional components not explicitly shown in FIG. 2, such as respective messaging interfaces that are utilized by the control modules 108 to generate control-to-routing messages for transmission to the routing modules 108R, and to process routing-to-control messages received from the routing modules 108R. Such messaging interfaces can also be configured to generate messages for transmission to the management module 108M and to process instructions and other messages received from the management module 108M.

The data modules 108D-1 through 108D-y in the FIG. 2 embodiment comprise respective control interfaces 210D-1 through 210D-y. These control interfaces 210D support communication between the data modules 108D and corresponding ones of the control modules 108C. Also included in the data modules 108D-1 through 108D-y are respective SSD interfaces 212D-1 through 212D-y. These SSD interfaces 212D support communications with corresponding ones of the storage devices 106.

The replication process is assumed to comprise a synchronous replication process in which write requests directed by one or more host devices to the source storage system are mirrored to the target storage system. For example, when a synchronous replication process is enabled for a particular logical storage volume or set of logical storage volumes, the source storage system mirrors host writes to the logical storage volume(s) to the target storage system as part of handling those host writes, and only responds to an initiating host after receiving acknowledgement of successful replication from the target storage system.

The term “write request” as used herein is intended to be broadly construed, so as to encompass one or more input-output (IO) operations directing that at least one data item of a storage system be written to in a particular manner. A given write request is illustratively received in the storage system 105 from one of the host devices 102. For example, in some embodiments, a write request is received in distributed storage controller 108 of the storage system 105, and directed from one processing module to another processing module of the distributed storage controller 108. More particularly, in the embodiment to be described below in conjunction with FIG. 3B, a received write request is directed from a routing module of the source storage system to a control module of the source storage system. Other arrangements for receiving and processing write requests from one or more host devices can be used.

As noted above, the replication process can additionally include a cycle-based asynchronous replication process in which the control modules 108C scan differences in designated replication data between replication cycles, and send corresponding data transfer requests as needed to the routing modules 108R. The routing modules 108R in turn replicate the data to a remote storage node cluster of the target storage system, and then respond to the control modules 108C regarding the data replication results.

The routing modules 108R illustratively comprise respective messaging interfaces and respective corresponding instances of replication control logic. These messaging interfaces are utilized by the corresponding instances of replication control logic to generate routing-to-control messages for transmission to one or more of the control modules 108C and to process control-to-routing messages received from one or more of the control modules 108C in conjunction with the replication process.

For example, as indicated above, a given one of the control modules 108C may be configured to generate a request message as a control-to-routing message for transmission to a given one of the routing modules 108R requesting that the given routing module transfer designated replication data to the target storage system.

The synchronous replication process in the present embodiment is therefore assumed to be carried out by the processing modules 108C, 108D, 108R and 108M. It is further assumed that the control modules 108C write data pages in the storage system 105 via the data modules 108D in accordance with write requests received from host devices 102 via the routing modules 108R. At least a subset of the host devices 102 illustratively comprise respective compute nodes of the computer system 101.

Execution of a given write request received in the storage system 105 from a host device illustratively involves the following operations:

1. Receive the write request in a particular control module 108C from a particular routing module 108R.

2. Acquire CIO address range lock for the logical address range to be written, where CIO refers to an IO process component in the control module 108C. As noted above, the control modules have ownership of particular logical address spaces, and the CIO address therefore denotes a global logical address for a given storage block.

3. Perform a read-modify operation if the write is a small or unaligned write. Examples of read-modify operations for use with small or unaligned writes can be found in the above-cited U.S. Pat. No. 9,104,326.

4. Write the data pages to a data module 108D, based on a hash-to-data (“H2D”) table. New hash handles are generated for the respective data pages, and reference counts associated with the new hash handles are incremented.

5. Release the CIO address range lock.

6. Send a response back to the requesting routing module 108R.

7. Decrement reference counts associated with the old hash handles of respective data pages that have been overwritten. These are examples of what are more generally referred to herein as “dereferencing operations.”

The reference counts mentioned above are illustratively maintained for respective physical blocks in the storage devices 106 and each such reference count indicates for its corresponding physical block the number of logical blocks that point to that same physical block. When all logical block references to a given physical block are removed, the reference count for that physical block becomes zero and its capacity can be released. A given “dereferencing operation” as that term is broadly used herein is intended to encompass decrementing of a reference count associated with a physical block.

In conjunction with release of logical address space in the storage system 105, the storage controller 108 makes the released logical address space available to users, executes dereferencing operations for respective ones of the physical blocks corresponding to the released logical address space, and releases any physical capacity for which the corresponding reference counts reach zero.

The logical address space illustratively comprises one or more ranges of logical block addresses or LBAs each comprising a LUN ID and an offset. For example, each LBA can identify a particular one of the user data pages 112. The LBAs each correspond to one or more physical blocks in the storage devices 106. Other types of LBAs and logical address spaces can be used in other embodiments. The term “logical address” as used herein is therefore intended to be broadly construed.

A given such logical address space may be released responsive to deletion of a corresponding storage volume, snapshot or any other arrangement of data stored in the storage system 105. Other conditions within the storage system 105 can also result in release of logical address space.

As indicated above, the storage controller 108 via its processing modules 108C, 108D, 108R and 108M is configured to implement synchronous replication failure recovery functionality utilizing multiple write journals in the storage system 105.

In this embodiment, the storage controller 108 is configured to implement a logical storage layer in which logical blocks are associated with respective content-based signatures and a physical storage layer in which the content-based signatures are associated with respective physical blocks in the storage devices 106. As part of this process, the storage controller 108 maintains reference counts for respective ones of the physical blocks, with a given such reference count indicating a number of the logical blocks that map via their respective content-based signatures to the same physical block.

In conjunction with the replication process being carried out by the processing modules 108C, 108D, 108R and 108M, a particular one of the control modules 108C detects a replication failure condition for a given write request received from one of the host devices 102, which may in some embodiments comprise a compute node of the computer system 101. The particular control module 108C provides a notification of the detected replication failure to the management module 108M.

The synchronous replication process in this embodiment is assumed to be configured such that the target storage system generates for each successfully mirrored write request a corresponding response back to the source storage system. This response generally comes from a routing module of the target storage system back to the particular control module that requested the data transfer for mirroring of the write request. The requesting control module would then normally provide a replication acknowledgement back to the host device that generated the write request, so as to indicate to the host device that the write request has been successfully mirrored to the target storage system.

The term “replication acknowledgement” as used herein is also intended to be broadly construed, so as to encompass any type of update, status report or other message that would ordinarily be provided by a processing module of a storage system to a host device responsive to a write request generated by that host device and directed to a data item that is subject to replication in the storage system.

The detected replication failure condition for the given write request therefore illustratively comprises a failure to receive in the requesting control module a corresponding response from the target storage system indicating that the given write request has been successfully mirrored to the target storage system. For example, the replication failure condition may be detected upon expiration of a specified timeout period without the expected successful mirroring response being received from the target storage system. The timeout period may be measured from transmission of a data transfer request from the requesting control module of the source storage system. Other types of replication failure conditions and failure detection mechanisms can be used in other embodiments.

The notification of the detected replication failure condition may be one of a plurality of such notifications received in the management module 108M from respective different ones of the control modules 108C.

Responsive to receipt of the notification of the detected replication failure condition, the management module 108M causes the replication process to enter a failure recovery mode of operation.

As a more particular example in the XtremIO™ context, synchronous replication failure recovery utilizing multiple journals is implemented across multiple processing modules of a distributed storage controller.

The C-modules, D-modules and R-modules of the storage nodes in this context are assumed to be configured to communicate with one another over a high-speed internal network such as an InfiniBand (TB) network. The C-modules, D-modules and R-modules coordinate with one another to accomplish various TO processing tasks.

The synchronous replication failure recovery functionality utilizing multiple write journals in this particular example is more specifically implemented as follows:

1. Receive in a given one of the C-modules a write request from a host device for one or more logical block addresses. The logical block addresses are in a portion of a logical storage volume, where that portion is “owned” by the given C-module.

2. Persist the write data in the appropriate D-module and/or in a write cache journal.

3. If the received write request is a multi-page write request, create a corresponding entry in an atomic transaction write journal to journal the write request. The atomic transaction write journal is used to make sure that either all pages of the multi-page write request are updated or none of the pages of the multi-page write request are updated.

4. If the received write request is not a multi-page write request, create a corresponding entry in a synchronous replication write journal to journal the write request.

5. Update the A2H table.

6. If an entry was created in the atomic transaction write journal, swap that entry into the synchronous replication write journal. The swapping of the entry is performed in an atomic manner, such that the entry is in only one of the journals at any given point in time.

7. If synchronous replication to the target storage system is successful, release the synchronous replication write journal.

A variety of different failure conditions may arise that result in the synchronous replication to the target storage system being unsuccessful. For example, the source storage system may crash before the write request is successfully replicated to the target storage system.

Responsive to a given failure, the failure recovery in this example proceeds in the following manner:

1. Access the atomic transaction write journal and the synchronous replication write journal.

2. If there is at least one entry in the atomic transaction write journal, first perform recovery utilizing the atomic transaction write journal, and then perform recovery utilizing the synchronous replication write journal.

3. If there is no entry in the atomic transaction write journal, perform recovery utilizing only the synchronous replication write journal.

The example failure recovery process described above is executed at the source site utilizing replication control logic instances 200 and 206C of the respective storage node processing modules 108M and 108C of the source storage system in combination with the write journals 204C. It is to be appreciated that the particular process steps are exemplary only, and can be varied in other embodiments.

Also, the particular interconnection and signaling arrangements illustrated for processing modules 108C, 108D and 108M in FIG. 2 are presented by way of example only, and can be varied in other embodiments.

In some embodiments, the replication control logic of these processing modules comprises at least a portion of a replication engine of the storage controller 108.

It should also be understood that the particular arrangement of storage controller processing modules 108C, 108D, 108R and 108M as shown in the FIG. 1 embodiment is presented by way of example only. Numerous alternative arrangements of processing modules of a distributed storage controller may be used to implement failure recovery functionality for synchronous replication in a clustered storage system in other embodiments.

Although illustratively shown as being implemented within the storage system 105, the storage controller 108 in other embodiments can be implemented at least in part within the computer system 101, in another system component, or as a stand-alone component coupled to the network 104.

The computer system 101 and storage system 105 in the FIG. 1 embodiment are assumed to be implemented using at least one processing platform each comprising one or more processing devices each having a processor coupled to a memory. Such processing devices can illustratively include particular arrangements of compute, storage and network resources. For example, processing devices in some embodiments are implemented at least in part utilizing virtual resources such as VMs or Linux containers (LXCs), or combinations of both as in an arrangement in which Docker containers or other types of LXCs are configured to run on VMs.

As a more particular example, the storage controller 108 can be implemented in the form of one or more LXCs running on one or more VMs. Other arrangements of one or more processing devices of a processing platform can be used to implement the storage controller 108. Other portions of the system 100 can similarly be implemented using one or more processing devices of at least one processing platform.

The computer system 101 and the storage system 105 may be implemented on respective distinct processing platforms, although numerous other arrangements are possible. For example, in some embodiments at least portions of the computer system 101 and the storage system 105 are implemented on the same processing platform. The storage system 105 can therefore be implemented at least in part within at least one processing platform that implements at least a subset of the host devices 102.

The term “processing platform” as used herein is intended to be broadly construed so as to encompass, by way of illustration and without limitation, multiple sets of processing devices and associated storage systems that are configured to communicate over one or more networks. For example, distributed implementations of the system 100 are possible, in which certain components of the system reside in one data center in a first geographic location while other components of the cluster reside in one or more other data centers in one or more other geographic locations that are potentially remote from the first geographic location. Thus, it is possible in some implementations of the system 100 for different ones of the host devices 102 to reside in different data centers than the storage system 105. Numerous other distributed implementations of one or both of the computer system 101 and the storage system 105 are possible. Accordingly, the storage system 105 can also be implemented in a distributed manner across multiple data centers.

It is to be appreciated that these and other features of illustrative embodiments are presented by way of example only, and should not be construed as limiting in any way.

Accordingly, different numbers, types and arrangements of system components such as computer system 101, host devices 102, network 104, storage system 105, storage devices 106, storage controller 108 and storage nodes 115 and 120 can be used in other embodiments.

It should be understood that the particular sets of modules and other components implemented in the system 100 as illustrated in FIG. 1 are presented by way of example only. In other embodiments, only subsets of these components, or additional or alternative sets of components, may be used, and such components may exhibit alternative functionality and configurations. For example, as indicated previously, in some illustrative embodiments a given content addressable storage system or other type of storage system with synchronous replication failure recovery functionality utilizing multiple journals can be offered to cloud infrastructure customers or other users as a PaaS offering.

Additional details of illustrative embodiments will now be described with reference to FIGS. 3 and 4.

As mentioned previously, FIG. 3 more particularly comprises two separate figures denoted FIG. 3A and FIG. 3B, each showing different views of respective portions of an information processing system 300.

Referring now to FIG. 3A, information processing system 300 in an illustrative embodiment comprises a source site data center 322S coupled to network 104. The source site data center 322S comprises a storage system 105S having storage devices 106S and an associated storage controller 108S. The source site data center 322S further comprises a set of production servers 324S coupled to the storage system 105S. The storage controller 108S comprises replication control logic 325S and write journals 326S.

The storage system 105S is assumed to comprise an instance of storage system 105 previously described in conjunction with FIGS. 1 and 2, although other types of storage systems can be used in other embodiments.

The source site data center 322S is coupled via one or more communication channels 304 of the network 104 to a target site data center 322T of the system 300. The target site data center 322T comprises a storage system 105T having storage devices 106T and an associated storage controller 108T. The target site data center 322T further comprises a set of recovery servers 324T coupled to the storage system 105T. The storage controller 108T comprises replication control logic 325T. In some implementations, the storage controller 108T can also comprise write journals and can be configured, for example, to support an option for synchronous replication in the reverse direction between the storage systems 105, although such write journals are not explicitly shown in the figure.

Like the storage system 105S, the storage system 105T is also assumed to comprise an instance of storage system 105 previously described in conjunction with FIGS. 1 and 2.

The source site data center 322S and the target site data center 322T are examples of what are more generally referred to herein as respective ones of a “source site” and a “target site” of an information processing system. The source site data center 322S and the target site data center 322T will therefore also be referred to herein as respective source site 322S and target site 322T of the system 300. In some embodiments, the target site 322T comprises a disaster recovery site data center and the source site 322S comprises a production site data center, although other arrangements are possible.

The source site 322S and target site 322T may be implemented in respective distinct local and remote geographic locations, although it is also possible for the two sites to be within a common facility or even implemented on a common processing platform.

It is assumed that data is replicated in system 300 from the source site 322S to the target site 322T using a replication process that begins in an asynchronous replication mode, and subsequently transitions from the asynchronous replication mode to a synchronous replication mode. For example, the asynchronous replication mode may be used to replicate the bulk of a given set of data from the storage system 105S to the storage system 105T. The mirroring functionality of the synchronous replication mode is then enabled. Other arrangements utilizing different replication modes and different transitions between the modes are possible. It is also possible that the system 300 can be configured to support only synchronous replication with no asynchronous replication.

The synchronous replication mode in some embodiments is illustratively configured to mirror data writes between the source and target storage systems 105S and 105T. For example, when a host device implementing one or more of the production servers 324S writes data to the source storage system 105S, the storage system 105S responds to the host device with an acknowledgement of successful storage in the storage system 105S only after the storage system 105S sends the data to the target storage system 105T and receives an acknowledgement of successful storage back from the storage system 105T.

An asynchronous replication mode in some embodiments performs cycle-based asynchronous replication to periodically transfer data in multiple cycles from the source site 322S to the target site 322T. The data replicated from the source site 322S to the target site 322T can include all of the data stored in the storage system 105S, or only certain designated subsets of the data stored in the storage system 105S, such as particular designated sets of LUNs or other logical storage volumes. Different replication processes of different types can be implemented for different parts of the stored data.

Further details regarding asynchronous replication processes suitable for use in illustrative embodiments herein can be found in U.S. patent application Ser. No. 15/662,809, filed Jul. 28, 2017 and entitled “Automatic Verification of Asynchronously Replicated Data,” which is incorporated by reference herein. Other embodiments need not utilize these automatic verification techniques, and can be implemented using alternative verification techniques as well as other types of replication processes. Accordingly, illustrative embodiments herein are not limited to use with cycle-based asynchronous replication, but are more generally applicable to other types of data replication.

A given “replication process” as that term is broadly used herein may therefore include both asynchronous and synchronous replication modes as well as support for concurrent operation of such modes and separate operation of the individual modes. The term “mode” as used herein in conjunction with asynchronous or synchronous replication may therefore itself comprise a corresponding asynchronous or synchronous replication process. It is also possible in some embodiments that a replication process may comprise only synchronous replication, instead of multiple distinct replication modes.

Each of the source site 322S and target site 322T in the FIG. 3A embodiment is assumed to be implemented using at least one processing platform each comprising one or more processing devices each having a processor coupled to a memory. Such processing devices can illustratively include particular arrangements of compute, storage and network resources. For example, processing devices in some embodiments are implemented at least in part utilizing virtual resources such as VMs or LXCs, or combinations of both as in an arrangement in which Docker containers or other types of LXCs are configured to run on VMs.

As a more particular example, the storage controllers 108S and 108T or various components thereof can each be implemented in the form of one or more LXCs running on one or more VMs. Other arrangements of one or more processing devices of a processing platform can be used to implement the storage controllers 108S and 108T and/or their respective components. Other portions of the system 300 can similarly be implemented using one or more processing devices of at least one processing platform.

The source site 322S and target site 322T are illustratively implemented on respective distinct processing platforms, although numerous other arrangements are possible. For example, in some embodiments at least portions of the source site 322S and the target site 322T may be implemented on the same processing platform. The term “processing platform” as used herein is intended to be broadly construed so as to encompass, by way of illustration and without limitation, multiple sets of processing devices and associated storage systems that are configured to communicate over one or more networks.

Referring now to FIG. 3B, a more detailed view of a portion of the information processing system 300 is shown, including processing modules of distributed storage controllers of the source storage system 105S and the target storage system 105T.

As illustrated, a portion of a distributed storage controller of the source storage system 105S comprises a plurality of control modules 308C-1 through 308C-x and a plurality of routing modules 308R-1 through 308R-x. The distributed storage controller of the storage system 105S is assumed to further comprise a plurality of data modules and at least one management module, although these additional processing modules are not shown in the figure for clarity and simplicity of illustration.

Similarly, a portion of a distributed storage controller of the target storage system 105T comprises a plurality of control modules 328C-1 through 328C-x and a plurality of routing modules 328R-1 through 328R-x. The distributed storage controller of the target storage system 105T is also assumed to further comprise a plurality of data modules and at least one management module, although these additional processing modules are not shown in the figure.

Also illustrated in FIG. 3B is a portion of a messaging flow associated with a particular host write that is to be replicated from the source storage system 105S (“source”) to the target storage system 105T (“target”) as part of a synchronous replication process or synchronous replication mode of the system 300.

The synchronous replication process flow for the given host write in this embodiment illustratively comprises the following steps:

1. Host write

2. Extent lock at source

3. Write at source

4. Transmit to target

5. Receive in target

6. Extent lock at target

7. Write at target

8. Release extent lock at target

9. Return status to source

10. Update A2H table locally at source

11. Release extent lock at source

12. Return status to host

In the figure, steps 1, 2 and 4-6 are illustrated by arrows. The extent lock refers to locking of a particular address range in conjunction with the host write. As mentioned previously herein, the A2H table updated in step 10 provides a mapping between logical addresses and corresponding content-based signatures of respective data pages. As the host write illustratively changes content of one or more such data pages, the content-based signatures and associated A2H table are updated in conjunction with the host write.

An example of a replication failure condition in this embodiment is a failure of the transmitting control module 308C-1 to receive an expected response from the target storage system 105T as part of the status report in step 9 above indicating that the given host write has been successfully mirrored to the target storage system 105T. Upon detection of such a replication failure condition, the control module 308C-1 provides a notification to a management module of the source storage system 105S.

One or more messages associated with returning status back to the host in step 12 of the synchronous replication messaging flow may therefore be viewed as an example of what is more generally referred to herein as a “replication acknowledgement.”

The other control modules 308C will operate in a similar manner to that described above for control module 308C-1, as instructed by the management module.

Again, it is to be appreciated that these and other features of illustrative embodiments are presented by way of example only, and should not be construed as limiting in any way. Accordingly, different numbers, types and arrangements of system components such as source and target sites 322S and 322T and their respective storage systems 105S and 105T and storage controllers 108S and 108T can be used in other embodiments. In these other embodiments, only subsets of these components, or additional or alternative sets of components, may be used, and such components may exhibit alternative functionality and configurations.

The replication process carried out between the source storage system 105S and the target storage system 105T in the FIG. 3 embodiment illustratively utilizes multiple journal techniques of the type previously described in conjunction with the storage system 105 of FIG. 1.

The operation of the information processing system 300 will now be described in further detail with reference to the flow diagram of the illustrative embodiment of FIG. 4. The process as shown includes steps 400 through 418, and is suitable for use in the system 300 but is more generally applicable to other types of information processing systems, including system 100 of FIG. 1, in which multiple storage systems are configured to participate in a replication process. The steps are illustratively performed by cooperative interaction of replication engines or other arrangements of replication control logic of respective storage controllers in respective source site and target storage systems, also referred to as simply respective “source” and “target” in the figure. A given such storage controller in a source site or target storage system can comprise a distributed storage controller such as storage controller 108 implemented in the manner illustrated in FIGS. 1 to 3.

In step 400, the source initiates a synchronous replication process to mirror host writes received from one or more host devices to the target. The synchronous replication process may be a synchronous replication mode of a replication process that includes both asynchronous and synchronous replication modes.

In step 402, the source receives a write request from a host.

In step 404, a determination is made as to whether or not the received write request is a multi-page write request. If the received write request is a multi-page write request, the process moves to step 406. Otherwise, the received write request is a single-page write request and the process moves to step 408.

In step 406, a corresponding entry is created in an atomic transaction write journal for the received write request.

In step 408, a corresponding entry is created in a synchronous replication write journal for the received write request.

Accordingly, a given received write request in the FIG. 4 embodiment will result in creation of an entry for that write request in either the atomic transaction write journal if the write request is a multi-page write request, or in the synchronous replication write journal if the write request is a single-page write request.

In step 410, an A2H table is updated in accordance with write data of the write request. In step 412, a determination is made as to whether or not an entry was created in the atomic transaction write journal via execution of step 406. If such an entry was created, the process moves to step 414, and otherwise skips step 414 and moves directly to step 416.

In step 414, the entry from the atomic transaction write journal is swapped into the synchronous replication write journal.

In step 416, the source sends the write data to the target.

In step 418, a determination is made as to whether or not the synchronous replication process has been ended. If the synchronous replication process has not ended, the FIG. 4 process returns to step 402 to process additional write requests, with each such request being processed using steps 404 through 416. Otherwise, the synchronous replication process is terminated and the FIG. 4 process steps as indicated in the figure.

The FIG. 4 process illustrates the maintenance of the atomic transaction write journal and the synchronous replication write journal in the source storage system. The manner in which synchronous replication failure recovery is implemented utilizing these two distinct journals will now be described in more detail.

Responsive to a failure in the synchronous replication process, different sets of one or more recovery operations are performed based at least in part on whether or not there is at least one entry remaining in the atomic transaction write journal.

For example, the failure in the synchronous replication process may occur after creation of the corresponding entry in the atomic transaction write journal in step 406 but prior to swapping of the entry from the atomic transaction write journal into the synchronous replication write journal in step 414. In this situation, there is at least one entry remaining in the atomic transaction write journal, and the set of one or more recovery operations performed responsive to the failure illustratively comprises a first recovery operation performed utilizing the atomic transaction write journal and a second recovery operation subsequently performed utilizing the synchronous replication write journal.

As another example, the failure in the synchronous replication process may occur after swapping of the entry from the atomic transaction write journal in step 414 into the synchronous replication write journal. In this situation, the set of one or more recovery operations performed responsive to the failure comprises a recovery operation performed utilizing the synchronous replication write journal but no recovery operation performed utilizing the atomic transaction write journal.

In some embodiments, recovery from these and other types of failures that may arise due to source or target crashes, link timeouts, link losses or other causes is performed in a particularly efficient manner through utilization of multiple write journals. For example, synchronization between source and target can be recovered for any failure occurring after completion of step 406 or step 408 for a given write request, as the process ensures that sufficient information is available from one of the journals to replay the write request. Failures occurring prior to that time are not an issue as the replication process basically treats the non-journaled write request as having not been received at all.

Recovery from any failure occurring after completion of step 406 or step 408 for a given write request generally involves determining if the atomic transaction write journal includes at least one entry, and if it does, recovering from the failure by first using the atomic transaction write journal and then recovering using the synchronous replication write journal. Otherwise, recovery utilizes only the synchronous replication write journal. Such arrangements ensure that any write requests that are “in flight” at the time of the failure are properly handled in the recovery operations. It is important in such embodiments that a given write request is journaled in either the atomic transaction write journal or the synchronous replication write journal but not in both journals. The swap of an entry from the atomic transaction write journal to the synchronous replication write journal is performed after the A2H table has been updated in step 410 for the given write request. Accordingly, the given write request is in only one of the two journals at any given time.

Other types of recovery operations may be applied in other types of failure situations in other embodiments, utilizing other types of write journals maintained in the source storage system in a manner similar to that illustrated in FIG. 4.

It is also to be appreciated that the FIG. 4 process and other features and functionality for synchronous replication failure recovery utilizing multiple write journals as described above can be adapted for use with other types of information systems, including by way of example an information processing system in which source and target storage systems are both implemented on the same processing platform.

The particular processing operations and other system functionality described in conjunction with the flow diagram of FIG. 4 are presented by way of illustrative example only, and should not be construed as limiting the scope of the disclosure in any way. Alternative embodiments can use other types of processing operations for implementing synchronous replication failure recovery functionality utilizing multiple write journals. For example, the ordering of the process steps may be varied in other embodiments, or certain steps may be performed at least in part concurrently with one another rather than serially. Also, one or more of the process steps may be repeated periodically, or multiple instances of the process can be performed in parallel with one another in order to implement a plurality of different replication processes for respective different sets of replicated data or for different storage systems or portions thereof within a given information processing system.

Functionality such as that described in conjunction with the flow diagram of FIG. 4 can be implemented at least in part in the form of one or more software programs stored in memory and executed by a processor of a processing device such as a computer or server. As will be described below, a memory or other storage device having executable program code of one or more software programs embodied therein is an example of what is more generally referred to herein as a “processor-readable storage medium.”

For example, a storage controller such as storage controller 108 that is configured to control performance of one or more steps of the FIG. 4 process can be implemented as part of what is more generally referred to herein as a processing platform comprising one or more processing devices each comprising a processor coupled to a memory. A given such processing device may correspond to one or more virtual machines or other types of virtualization infrastructure such as Docker containers or other types of LXCs. The storage controller 108, as well as other system components, may be implemented at least in part using processing devices of such processing platforms. For example, in a distributed implementation of the storage controller 108, respective distributed modules of such a storage controller can be implemented in respective LXCs running on respective ones of the processing devices of a processing platform.

In some embodiments, the source and target storage systems comprise respective XtremIO™ storage arrays suitably modified to incorporate synchronous replication failure recovery functionality utilizing multiple journals as disclosed herein. As described previously, in the context of an XtremIO™ storage array, the control modules 108C, data modules 108D, routing modules 108R and management module(s) 108M of the distributed storage controller 108 in system 100 illustratively comprise C-modules, D-modules, R-modules and SYM module(s), respectively. These exemplary processing modules of the distributed storage controller 108 can be configured to implement synchronous replication failure recovery utilizing multiple journals maintained in accordance with the FIG. 4 process.

The replication techniques utilizing multiple journals implemented in the embodiments described above can be varied in other embodiments. For example, different types of process operations can be used in other embodiments.

In addition, the above-described functionality associated with C-module, D-module, R-module and SYM module components of an XtremIO™ storage array can be incorporated into other processing modules or components of a centralized or distributed storage controller in other types of storage systems.

Illustrative embodiments of content addressable storage systems or other types of storage systems with synchronous replication failure recovery functionality utilizing multiple journals as disclosed herein can provide a number of significant advantages relative to conventional arrangements.

For example, some embodiments provide techniques for efficient recovery from a failure in a synchronous replication process carried out between source and target storage systems in an information processing system.

Such embodiments can more accurately account for write requests that are already being processed or “in flight” when a failure occurs in the synchronous replication process. The resilience and reliability of the synchronous replication process in the presence of failures is thereby enhanced.

Accordingly, illustrative embodiments provide more accurate and efficient recovery from synchronous replication failures than conventional approaches. For example, one or more such embodiments avoid the need for a time-consuming full data re-synchronization of replicated storage objects between the source and target storage systems.

These and other embodiments include clustered storage systems comprising storage controllers that are distributed over multiple storage nodes. Similar advantages can be provided in other types of storage systems.

It is to be appreciated that the particular advantages described above and elsewhere herein are associated with particular illustrative embodiments and need not be present in other embodiments. Also, the particular types of information processing system features and functionality as illustrated in the drawings and described above are exemplary only, and numerous other arrangements may be used in other embodiments.

As mentioned previously, at least portions of the information processing systems 100 and 300 may be implemented using one or more processing platforms. A given such processing platform comprises at least one processing device comprising a processor coupled to a memory. The processor and memory in some embodiments comprise respective processor and memory elements of a virtual machine or container provided using one or more underlying physical machines. The term “processing device” as used herein is intended to be broadly construed so as to encompass a wide variety of different arrangements of physical processors, memories and other device components as well as virtual instances of such components. For example, a “processing device” in some embodiments can comprise or be executed across one or more virtual processors. Processing devices can therefore be physical or virtual and can be executed across one or more physical or virtual processors. It should also be noted that a given virtual device can be mapped to a portion of a physical one.

Some illustrative embodiments of a processing platform that may be used to implement at least a portion of an information processing system comprise cloud infrastructure including virtual machines implemented using a hypervisor that runs on physical infrastructure. The cloud infrastructure further comprises sets of applications running on respective ones of the virtual machines under the control of the hypervisor. It is also possible to use multiple hypervisors each providing a set of virtual machines using at least one underlying physical machine. Different sets of virtual machines provided by one or more hypervisors may be utilized in configuring multiple instances of various components of the system.

These and other types of cloud infrastructure can be used to provide what is also referred to herein as a multi-tenant environment. One or more system components such as source and target storage systems 105S and 105T, or portions thereof, are illustratively implemented for use by tenants of such a multi-tenant environment.

As mentioned previously, cloud infrastructure as disclosed herein can include cloud-based systems such as AWS, GCP and Microsoft Azure. Virtual machines provided in such systems can be used to implement at least portions of one or more of a computer system and a content addressable storage system in illustrative embodiments. These and other cloud-based systems in illustrative embodiments can include object stores such as Amazon S3, GCP Cloud Storage, and Microsoft Azure Blob Storage.

In some embodiments, the cloud infrastructure additionally or alternatively comprises a plurality of containers implemented using container host devices. For example, a given container of cloud infrastructure illustratively comprises a Docker container or other type of LXC. The containers may run on virtual machines in a multi-tenant environment, although other arrangements are possible. The containers may be utilized to implement a variety of different types of functionality within the system 100 or 300. For example, containers can be used to implement respective processing devices providing compute and/or storage services of a cloud-based system. Again, containers may be used in combination with other virtualization infrastructure such as virtual machines implemented using a hypervisor.

Illustrative embodiments of processing platforms utilized to implement host devices and storage systems with synchronous replication failure recovery functionality utilizing multiple write journals will now be described in greater detail with reference to FIGS. 5 and 6. Although described in the context of system 100, these platforms may also be used to implement at least portions of other information processing systems in other embodiments.

FIG. 5 shows an example processing platform comprising cloud infrastructure 500. The cloud infrastructure 500 comprises a combination of physical and virtual processing resources that may be utilized to implement at least a portion of the information processing system 100. The cloud infrastructure 500 comprises multiple virtual machines (VMs) and/or container sets 502-1, 502-2, . . . 502-L implemented using virtualization infrastructure 504. The virtualization infrastructure 504 runs on physical infrastructure 505, and illustratively comprises one or more hypervisors and/or operating system level virtualization infrastructure. The operating system level virtualization infrastructure illustratively comprises kernel control groups of a Linux operating system or other type of operating system.

The cloud infrastructure 500 further comprises sets of applications 510-1, 510-2, . . . 510-L running on respective ones of the VMs/container sets 502-1, 502-2, . . . 502-L under the control of the virtualization infrastructure 504. The VMs/container sets 502 may comprise respective VMs, respective sets of one or more containers, or respective sets of one or more containers running in VMs.

In some implementations of the FIG. 5 embodiment, the VMs/container sets 502 comprise respective VMs implemented using virtualization infrastructure 504 that comprises at least one hypervisor. Such implementations can illustratively provide at least portions of the functionality described above. For example, one or more of the VMs can be configured to implement at least a portion of a storage controller and its associated replication control logic and other modules for providing synchronous replication failure recovery functionality utilizing multiple write journals in the system 100.

An example of a hypervisor platform that may be used to implement a hypervisor within the virtualization infrastructure 504 is the VMware® vSphere® which may have an associated virtual infrastructure management system such as the VMware® vCenter™. The underlying physical machines may comprise one or more distributed processing platforms that include one or more storage systems.

In other implementations of the FIG. 5 embodiment, the VMs/container sets 502 comprise respective containers implemented using virtualization infrastructure 504 that provides operating system level virtualization functionality, such as support for Docker containers running on bare metal hosts, or Docker containers running on VMs. The containers are illustratively implemented using respective kernel control groups of the operating system. Such implementations can also illustratively provide at least portions of the functionality described above. For example, a container host device supporting multiple containers of one or more container sets can be configured to implement at least a portion of a storage controller and its associated replication control logic and other modules for providing synchronous replication failure recovery functionality utilizing multiple write journals in the system 100.

As is apparent from the above, one or more of the processing modules or other components of system 100 may each run on a computer, server, storage device or other processing platform element. A given such element may be viewed as an example of what is more generally referred to herein as a “processing device.” The cloud infrastructure 500 shown in FIG. 5 may represent at least a portion of one processing platform. Another example of such a processing platform is processing platform 600 shown in FIG. 6.

The processing platform 600 in this embodiment comprises a portion of system 100 and includes a plurality of processing devices, denoted 602-1, 602-2, 602-3, . . . 602-K, which communicate with one another over a network 604.

The network 604 may comprise any type of network, including by way of example a global computer network such as the Internet, a WAN, a LAN, a satellite network, a telephone or cable network, a cellular network, a wireless network such as a WiFi or WiMAX network, or various portions or combinations of these and other types of networks.

The processing device 602-1 in the processing platform 600 comprises a processor 610 coupled to a memory 612.

The processor 610 may comprise a microprocessor, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a graphics processing unit (GPU), or other type of processing circuitry, as well as portions or combinations of such circuitry elements.

The memory 612 may comprise random access memory (RAM), read-only memory (ROM), flash memory or other types of memory, in any combination. The memory 612 and other memories disclosed herein should be viewed as illustrative examples of what are more generally referred to as “processor-readable storage media” storing executable program code of one or more software programs.

Articles of manufacture comprising such processor-readable storage media are considered illustrative embodiments. A given such article of manufacture may comprise, for example, a storage array, a storage disk or an integrated circuit containing RAM, ROM, flash memory or other electronic memory, or any of a wide variety of other types of computer program products. The term “article of manufacture” as used herein should be understood to exclude transitory, propagating signals. Numerous other types of computer program products comprising processor-readable storage media can be used.

Also included in the processing device 602-1 is network interface circuitry 614, which is used to interface the processing device with the network 604 and other system components, and may comprise conventional transceivers.

The other processing devices 602 of the processing platform 600 are assumed to be configured in a manner similar to that shown for processing device 602-1 in the figure.

Again, the particular processing platform 600 shown in the figure is presented by way of example only, and system 100 may include additional or alternative processing platforms, as well as numerous distinct processing platforms in any combination, with each such platform comprising one or more computers, servers, storage devices or other processing devices.

For example, other processing platforms used to implement illustrative embodiments can comprise converged infrastructure such as VxRail™, VxRack™, VxRack™ FLEX, VxBlock™ or Vblock® converged infrastructure from VCE, the Virtual Computing Environment Company, now the Converged Platform and Solutions Division of Dell EMC.

It should therefore be understood that in other embodiments different arrangements of additional or alternative elements may be used. At least a subset of these elements may be collectively implemented on a common processing platform, or each such element may be implemented on a separate processing platform.

As indicated previously, components of an information processing system as disclosed herein can be implemented at least in part in the form of one or more software programs stored in memory and executed by a processor of a processing device. For example, at least portions of the synchronous replication failure recovery functionality of one or more components of a storage system as disclosed herein are illustratively implemented in the form of software running on one or more processing devices.

It should again be emphasized that the above-described embodiments are presented for purposes of illustration only. Many variations and other alternative embodiments may be used. For example, the disclosed techniques are applicable to a wide variety of other types of information processing systems, host devices, storage systems, storage nodes, storage devices, storage controllers, write journals, replication control logic and other components. Also, the particular configurations of system and device elements and associated processing operations illustratively shown in the drawings can be varied in other embodiments. Moreover, the various assumptions made above in the course of describing the illustrative embodiments should also be viewed as exemplary rather than as requirements or limitations of the disclosure. Numerous other alternative embodiments within the scope of the appended claims will be readily apparent to those skilled in the art. 

What is claimed is:
 1. An apparatus comprising: a storage system comprising a plurality of storage devices and a storage controller; the storage system being configured to participate as a source storage system in a synchronous replication process with a target storage system; wherein in conjunction with the synchronous replication process, the source storage system is further configured: to receive write requests from at least one host device; for each of the received write requests: responsive to the write request being a multi-page write request, to create a corresponding entry in a first journal for the write request, where the first journal is utilized to ensure that the given write request is completed for all multiple pages or for none of the multiple pages; responsive to the write request being a single-page write request, to create a corresponding entry in a second journal different than the first journal; to update an address-to-signature table utilizing write data of the write request; if the corresponding entry for the write request was created in the first journal, to swap an entry from the first journal into the second journal; and to send the write data of the write request to the target storage system; wherein responsive to a failure in the synchronous replication process, different sets of one or more recovery operations are performed based at least in part on whether or not there is at least one entry remaining in the first journal; and wherein the source storage system is implemented using at least one processing device comprising a processor coupled to a memory.
 2. The apparatus of claim 1 wherein the first journal comprises an atomic transaction write journal and the second journal comprises a synchronous replication write journal.
 3. The apparatus of claim 1 wherein swapping the entry from the first journal into the second journal is performed in an atomic manner that ensures that the entry is in only one of the journals at any given time.
 4. The apparatus of claim 1 wherein the first and second journals are released responsive to successful completion of the synchronous replication process.
 5. The apparatus of claim 1 wherein the failure in the synchronous replication process occurs after creation of the corresponding entry in the first journal but prior to swapping of the entry from the first journal into the second journal and wherein the set of one or more recovery operations performed responsive to the failure comprises a first recovery operation performed utilizing the first journal and a second recovery operation subsequently performed utilizing the second journal.
 6. The apparatus of claim 1 wherein the failure in the synchronous replication process occurs after swapping of the entry from the first journal into the second journal and wherein the set of one or more recovery operations performed responsive to the failure comprises a recovery operation performed utilizing the second journal but no recovery operation performed utilizing the first journal.
 7. The apparatus of claim 1 wherein the source and target storage systems comprise respective content addressable storage systems having respective sets of non-volatile memory storage devices.
 8. The apparatus of claim 1 wherein the source and target storage systems are associated with respective source and target sites of the synchronous replication process and wherein the source site comprises a production site data center and the target site comprises a disaster recovery site data center.
 9. The apparatus of claim 1 wherein the source storage system comprises a plurality of storage nodes each comprising one or more of the storage devices and wherein each of the storage nodes of the target storage system further comprises a set of processing modules configured to communicate over one or more networks with corresponding sets of processing modules on other ones of the storage nodes, the sets of processing modules of the storage nodes of the source storage system collectively comprising at least a portion of the storage controller of the source storage system.
 10. The apparatus of claim 9 wherein each of the sets of processing modules comprises one or more control modules, one or more routing modules and one or more data modules, and wherein at least one of the sets of processing modules comprises a management module.
 11. The apparatus of claim 10 wherein the address-to-signature table on a given one of the storage nodes is maintained by a corresponding one of the one or more control modules of that storage node.
 12. The apparatus of claim 10 wherein local copies of the first and second journals are stored on respective ones of the storage nodes and wherein a given such local copy of the first or second journal for one of the storage nodes also represents a remote copy of that journal for one or more other ones of the storage nodes.
 13. The apparatus of claim 1 wherein at least one of the first and second journals is implemented as a sub-type of an additional journal utilized in updating of the address-to-signature table.
 14. The apparatus of claim 1 wherein the address-to-signature table maintained by the source storage system comprises at least one address-to-hash table of the source storage system, and wherein entries of the address-to-hash table comprise respective ones of a plurality of logical addresses in association with respective hash handles corresponding to respective content-based signatures.
 15. A method comprising: configuring a storage system to participate as a source storage system in a synchronous replication process with a target storage system; and in conjunction with the synchronous replication process, the source storage system: receiving write requests from at least one host device; for each of the received write requests: responsive to the write request being a multi-page write request, creating a corresponding entry in a first journal for the write request, where the first journal is utilized to ensure that the given write request is completed for all of the multiple pages or for none of the multiple pages; responsive to the write request being a single-page write request, creating a corresponding entry in a second journal different than the first journal; updating an address-to-signature table utilizing write data of the write request; if the corresponding entry for the write request was created in the first journal, swapping an entry from the first journal into the second journal; and sending the write data of the write request to the target storage system; wherein responsive to a failure in the synchronous replication process, different sets of one or more recovery operations are performed based at least in part on whether or not there is at least one entry remaining in the first journal; and wherein the method is implemented by at least one processing device comprising a processor coupled to a memory.
 16. The method of claim 15 wherein the failure in the synchronous replication process occurs after creation of the corresponding entry in the first journal but prior to swapping of the entry from the first journal into the second journal and wherein the set of one or more recovery operations performed responsive to the failure comprises a first recovery operation performed utilizing the first journal and a second recovery operation subsequently performed utilizing the second journal.
 17. The method of claim 15 wherein the failure in the synchronous replication process occurs after swapping of the entry from the first journal into the second journal and wherein the set of one or more recovery operations performed responsive to the failure comprises a recovery operation performed utilizing the second journal but no recovery operation performed utilizing the first journal.
 18. A computer program product comprising a non-transitory processor-readable storage medium having stored therein program code of one or more software programs, wherein the program code when executed by at least one processing device causes said at least one processing device: to configure a storage system to participate as a source storage system in a synchronous replication process with a target storage system; and in conjunction with the synchronous replication process, to configure the source storage system: to receive write requests from at least one host device; for each of the received write requests: responsive to the write request being a multi-page write request, to create a corresponding entry in a first journal for the write request, where the first journal is utilized to ensure that the given write request is completed for all of the multiple pages or for none of the multiple pages; responsive to the write request being a single-page write request, to create a corresponding entry in a second journal different than the first journal; to update an address-to-signature table utilizing write data of the write request; if the corresponding entry for the write request was created in the first journal, to swap an entry from the first journal into the second journal; and to send the write data of the write request to the target storage system; wherein responsive to a failure in the synchronous replication process, different sets of one or more recovery operations are performed based at least in part on whether or not there is at least one entry remaining in the first journal.
 19. The computer program product of claim 18 wherein the failure in the synchronous replication process occurs after creation of the corresponding entry in the first journal but prior to swapping of the entry from the first journal into the second journal and wherein the set of one or more recovery operations performed responsive to the failure comprises a first recovery operation performed utilizing the first journal and a second recovery operation subsequently performed utilizing the second journal.
 20. The computer program product of claim 18 wherein the failure in the synchronous replication process occurs after swapping of the entry from the first journal into the second journal and wherein the set of one or more recovery operations performed responsive to the failure comprises a recovery operation performed utilizing the second journal but no recovery operation performed utilizing the first journal. 